Configuration Carriers Carrier Services Carrier Services view Carrier Services form), and then reopen the vessel.If XPS detects errors during a test read or import, the XPS client displays those errors in the EDI window or, if the error is related to the equiv files, in the EDI Translator Log window.
Most EDI import errors are local so that you can resolve them immediately. The following internal errors are most common:
The wrong EDI format was selected.
The wrong file was selected and imported.
Code(s) in the incoming data do not have proper equivalents in your translation file, called the equiv file.
In such cases, the XPS client displays the EDI Translator Log window, which lists and describes the errors. Resolving this type of error requires changes to the equiv or codes files.
The vessel service or port rotation does not properly list the load and discharge ports.
If a load or discharge port is not in the vessel’s service, the XPS client displays a message in the EDI window. To add the valid ports to the vessel service, close the vessel, update the vessel’s service in the N4 client (N4 client Configuration Carriers Carrier Services Carrier Services view Carrier Services form), and then reopen the vessel.
ROB containers cover projected or planned loads.
This problem may occur if you import EDI data after you have started planning the vessel. Because you cannot override the actual inbound stow, you must replan your projected or planned loads.
If you cannot correct an EDI problem yourself, the error may be external. Contact the sender and determine if it is a problem in the sender’s procedure. If there is no procedural error, the data may have been corrupted in transmission. In such a case, ask the sender to retransmit the data and repeat the import procedure.
If a problem persists, contact Navis Technical Support.